-
Notifications
You must be signed in to change notification settings - Fork 299
Add 'how to define spans' meta-guidance #3240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| Don't try to capture all available properties as span attributes. Telemetry is | ||
| lossy, and it's important to assess the value-to-cost ratio of each referenced attribute. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't follow the tie in to being lossy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moved this to attributes section and replaced with
Only include attributes that bring clear value - this allows keeping telemetry
volume and performance overhead low. Don't try to capture all available details.
When in doubt, don't reference additional attributes - they can be added incrementally
based on feedback.
| - When the span starts and ends. | ||
| - If this span represents a client call, specify whether it captures the logical call | ||
| (as observed by the API caller) or the physical call (per-try/per-attempt). | ||
| - Define a span per different operation type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this is saying, maybe a short example could help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated to
- Define a different span for different operations - e.g., when spans have different
kinds or a significantly different set of attributes.
For example, HTTP client and server spans are two independent definitions.
Messaging publishing and receiving are also different span types.
0b17b67 to
a2914f1
Compare
Fixes #1853